In the TZ GEPG Reconciliation process, the bank team provides a reconciliation file in .xml format,
along with the specific date for which the transactions need to be cleared or marked as successful.
This file typically contains transaction details that failed or remained in an unresolved state
during earlier processing. Based on the provided date, the system identifies and processes the
corresponding records in Rover. These transactions are either cleared or flagged as successfully
processed to ensure consistency between the bank's ledger and the Rover system. This step is crucial
for maintaining data accuracy, preventing duplicate entries, and allowing the customer to proceed
with a clean transaction retry if needed.
✨TZ GEPG Reconciliation
Transaction Reconciliation & Management System
Operation Title: TZ GEPG Recon
Over view: In TZ GEPG Recon we can clear the transaction.
Key Features:
- Functionality for TZGEPG Recon
- Refresh of Red Circular Arrows
- Region Selection (Precondition)
- GePG Recon records Table
- Select a Date, Enter CURL Command, Click Send and View Response
- Final Output – TZ GEPG Recon Results
List of Figures:
- Figure 6.1 – Search Bar for filtering Case ID or File Name
- Figure 6.2 – Refresh Button with Red Circular Arrows
- Figure 6.3 – Region Selection from Navbar (Precondition)
- Figure 6.4 – Calendar Date Picker for Bank-Provided Date
- Figure 6.5 – CURL Command Input Field GePG Reconciliation
📋 Overview
🚀 Introduction
The TZ GEPG Reconciliation process is designed to ensure accurate alignment between the bank's transaction records and the Rover system. This module addresses discrepancies that may occur due to failed, incomplete, or duplicated transactions. By leveraging input from the bank team typically in the form of an .xml file and a specific transaction date Rover administrators can identify affected records and either clear or mark them as successfully processed. This not only maintains transactional consistency and audit accuracy but also enables customers to seamlessly retry failed operations without conflicts or duplication.
⚙️ Functionality
Figure: 6.1
1
🔍 Search Bar
Users can search for specific files by entering text like a case ID or filename. This makes it easier to quickly find the needed file without browsing through the whole list.
2
🔄 Refresh the Page
Red Circular Arrows: Refresh the page or API status latest updated data.
Figure: 6.2
Figure: 6.3
NOTE: Before opening the TZ-gepg recon form, users must select the region from
navbar.
📊 TZ Gepg Recon Records Table
1
TZ Gepg Recon Records Table:
📋 Reconciliation Process Steps:
- Select a Date: Click on the calendar icon and choose the desired date for reconciliation which was sent by the bank team.
- Enter cURL Command: In the input box labelled "Paste your cURL command here", enter your complete cURL command.
- Click Send: After entering the required details, click the Send button to submit the request.
- View Response: The interface will process the command and display the response received from the TZ-GePG API.
📅 Date Selection
Here, users can select the specific date provided by the bank team for processing or reconciliation. This ensures that only the relevant transactions for that date are reviewed, cleared, or updated within the system.
Figure: 6.4
💻 CURL Command Execution
In this section, users can paste the CURL command to execute and clear the specified GEPG transactions. Once executed, the system processes the given transaction IDs and performs the reconciliation. This allows customers to retry the cleared transactions without encountering duplicates or errors.
Figure: 6.5
🎯 Final Output
Once the reconciliation file and specified date are processed, the system identifies and clears or marks the listed transactions as successful. These updates ensure alignment between the bank's records and the Rover system. As a result, the previously failed or unresolved transactions are no longer active, allowing customers to retry them without errors or duplication maintaining accuracy and consistency across systems.